Skip to main content

No Code Flows: Frequently Asked Questions

What is EmpowerID's No Code Flows?

EmpowerID's No Code Flows is a system that provides a way to automate complex business processes without the need for traditional coding. It uses a component-based architecture with predefined elements to connect different stages of a business process.

What are the core components of No Code Flows?

The core components are:

  • Flow Events
  • Flow Items
  • Flow Definitions
  • Flow Policies
What is a Flow Event?

Flow Events are the starting point of any workflow and act as triggers that initiate a business process. For example, a Flow Event could be triggered when a new employee joins the organization or when a mailbox is discovered.

What are some examples of Flow Events?

Some examples include:

  • Mailbox Discovered – When a new mailbox is detected
  • Account Takeover – When potential unauthorized access is detected
  • Person Leaver – When someone leaves the organization
  • Person Joiner – When someone joins the organization
  • Person Mover – When someone moves within the organization
  • Person Rehire – When someone is rehired
What are Flow Items?

Flow Items are specific tasks or actions performed in response to Flow Events. They contain parameters that define the action, target, and scope of resources affected. For example, if a Person Leaver event is detected, Flow Items could include actions like "Remove this person from all groups" and "Disable all accounts belonging to this person."

What parameters do Flow Items contain?

Flow Items contain:

  • Item Type Action – Specifies the exact task to be executed
  • Item Type Scope – Determines the range within which the Item Type Action will execute
  • Item Collection Query – An SQL statement that retrieves specific resource data related to the Flow Item
What is a Flow Definition?

A Flow Definition is a set of instructions that holds one or more Flow Items. It serves as a template for business processes, outlining how Flow Items are orchestrated in response to a specific Flow Event.

What role do Flow Policies play?

Flow Policies act as a bridge between specific events and their corresponding automated responses. They determine which Flow Definitions to trigger in response to certain Flow Events and allow multiple rules for a single event.

How does the typical No Code Flow execution process work?

The process follows these steps:

  1. Flow initiates with an event
  2. Event is added to the Event Inbox
  3. Applicable policies determine flows to be run
  4. Flows are added to the Flow Inbox
  5. Each flow creates a Business Request
  6. Business Request creates Business Request Items
  7. Flow Definition manages sequence and timing
  8. Items requiring approval are sent for approval
  9. Approved items are sent to Business Request Fulfillment Engine
What are Business Requests?

Business Requests are generated when an event triggers a Flow Definition. They represent a formal request to execute the actions defined in the definition.

What are Business Request Items?

Business Request Items are individual tasks or actions that need to be executed as part of a Business Request. They are generated based on the Flow Definition and contain data such as request details, assignee ID, and resource ID.

What are Approval Flow Policies?

Approval Flow Policies are used to direct Business Requests to the appropriate people for approval. For example, if a person changes their location within the organization, that change could be routed to the person's manager for approval before certain resources are allocated to that person. If the Business Request is linked to an Approval Flow policy, the request could route for approval based on the assigned policies or be overridden and executed without requiring approval, as might be the case in person-leaver events.

What are Fulfillment Workflows?

Fulfillment Workflows are workflows that handle request items once approved, auto-approved, or rejected. They execute actions based on the Approval Flow outcome.